Automated pill dispenser

ABSTRACT

Disclosed is an automated pill dispenser, which provide a plurality of pill dispensing modules. The plurality of pill dispensing modules may have a first pill dispensing module and a second first pill dispensing module, and the first pill dispensing module has a first dispensing belt that dispenses a first individual pill and the second pill dispensing module having a second dispensing belt dispenses a second individual pill. One or more sensors may be used to monitor operation of the automated pill dispenser for dispensing medication by the plurality of pill dispensing modules. Also disclosed is a cloud-based resource and information tracking services for medical patients and healthcare providers and a hardware device that solves significant healthcare problems.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a Continuation of U.S. Application Serial No.17/221512, filed on Apr. 2, 2021, now issued as U.S. Pat. No.11,610,657, which is a Continuation of U.S. Application Serial No.16/043,112, filed on Jul. 23, 2018, now issued as U.S. Pat. No.10,984,901, which is a Continuation-In-Part of U.S. Application SerialNo. 14/575,880, filed on Dec. 18, 2014, now issued as U.S. Pat. No.10,032,004, which claims the benefit of priority to U.S. ProvisionalApplication No. 61/917,853, filed on Dec. 18, 2013, all of which arehereby incorporated by reference in their entirety.

BACKGROUND

The healthcare IT (information technology) marketplace is currentlydominated by IT systems that are relatively inefficient and lackstate-of-the-art technology. The lack of efficient, sophisticated ITsystems and services that address the rapid changes in the healthcareindustry is a serious impediment to reducing service costs and improvingthe quality of healthcare.

These problems are further exacerbated by modern governmental policiesand regulations, where governments continue to reduce and limitcompensation for critical services and patients. Governments now alsoexpect healthcare providers to offer ongoing preventive care, especiallyfor chronic conditions, even when the patient is not actively under aphysician’s care. While many single-point solutions exist, theirisolation from other systems and limited scope reduces theireffectiveness in providing satisfactory solutions to critical problems.Additionally, since no single healthcare IT service provider offers acost effective, comprehensive solution that addresses all the needs ofhealthcare providers and patients, each caregiver organization mustpiece together a “custom” solution on their own.

Consequently, there is a significant need for a universally accessible,fully integrated, intelligent solution that helps improve the quality ofcare while improving efficiency.

SUMMARY

Embodiments of the present invention provide an automated pilldispenser. Some embodiments provide a plurality of pill dispensingmodules, where the plurality of pill dispensing modules has a first pilldispensing module and a second first pill dispensing module, and thefirst pill dispensing module has a first dispensing belt that dispensesa first individual pill and the second pill dispensing module having asecond dispensing belt dispenses a second individual pill. Each of thefirst and second dispensing belts may be driven by a drive motor, whereeach of the plurality of dispensing belts corresponds to a separatemedication for delivery. One or more sensors may be used to monitoroperation of the automated pill dispenser for dispensing medication bythe plurality of pill dispensing modules. Also disclosed is acloud-based resource and information tracking services for medicalpatients and healthcare providers and a hardware device that solvessignificant healthcare problems, including the problems described above.

Other additional objects, features, and advantages of the invention aredescribed in the detailed description, figures, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 provides an illustration of an example architecture that can beused in some embodiments of the invention to implement the integrationplatform.

FIG. 2 is an illustration of the integration of the integrationplatform, remote dispenser control software, the dispenser controllerand the dispenser.

FIG. 3 is a side view of the console, modules, DC drive motor with wormdrive, bracket for DC motor, transverse belt, dispenser cup, dispensercup locking mechanisms, sensors and sensor mounts.

FIG. 4 is an angled view of the console, modules, cross feed DC drivemotor, bracket for DC motor, transverse belt, dispenser cup, dispensercup locking mechanisms and LCD screen.

FIG. 5 is a side view and cutaway view of the transverse belt mechanism:belt, side rails and pulleys.

FIG. 6 is a top and side view of the transverse belt mechanism: belt,side rails and pulleys.

FIG. 7 is side view and component view of the module, paddle wheel, DCmotor drive, module with module top and belt with paddle wheels.

FIG. 8 is side view and component view of the module, paddle wheel, DCmotor drive, belt with paddle wheels and details of the “bump” forreleasing stuck pills.

FIG. 9 shows details of the dispenser cup and software-controlledlocking mechanism.

FIG. 10A is a top view of a belt and cog assembly.

FIG. 10B is a front view of a belt and cog assembly.

FIG. 10C is a perspective view of a belt and cog assembly.

FIG. 11A is a top view of a cleat.

FIG. 11B is a front view of a cleat.

FIG. 11C is a side view of a cleat.

FIG. 11D is a rear view of a cleat.

FIG. 11E is an angled view of a cleat.

FIG. 12A is a top view of a pin.

FIG. 12B is a side view of a pin.

FIG. 12C is a front view of a pin.

FIG. 12D is an angled view of a pin.

FIG. 13A is a side view of a cartridge.

FIG. 13B is an angled view of a cartridge.

FIG. 14 illustrates a stacked set of cartridges.

FIG. 15 illustrates a horizontal alignment of cartridges relative to atransverse belt.

DETAILED DESCRIPTION

The figures and the following description relate to certain embodimentsof the present disclosure by way of illustration only. It should benoted that in the following discussion, alternative embodiments of thestructures and methods disclosed herein will be readily recognized asviable alternatives that may be employed without departing from theprinciples of the present disclosure. Reference will now be made indetail to several embodiments of the present disclosure(s), examples ofwhich are illustrated in the accompanying figures. It is noted thatwherever practicable similar or like reference numbers may be used inthe figures and may indicate similar or like functionality. The figuresdepict embodiments of the present disclosure for purposes ofillustration only. One skilled in the art will readily recognize fromthe following description that alternative embodiments of the structuresand methods illustrated herein may be employed without departing fromthe principles of the disclosure described herein.

Integration Platform

In some embodiments, the invention pertains to a cloud-based softwaresystem that integrates all/many sources of patient medical and healthinformation, updates the information in near real-time, and makes thedata available to each member of the patient’s healthcare team securely,anytime and anywhere Internet access is available.

FIG. 1 provides an illustration of an example architecture that can beused in some embodiments of the invention to implement an integrationplatform 28. The system 28 integrates information from doctors’ offices,hospitals, test labs, state organizations, remote and mobile devices andother sources. To accomplish this goal, the inventive approach isflexible enough to handle differences in information sources fordifferent types of users and different user requirements.

A high-performance database 29 that serves as a data repository is thebasis for the software product and services. Additional logic modulesprovide information 30 and business management services 31. Together,the database 29 and the information 30 and business management logicmodules 31 comprise the integration platform 28 that manages data andinformation collected and/or generated by the system. The integrationplatform’s modular design allows the addition of new data sourceswithout a disruption to an existing user’s service and allows eachuser’s experience to be customized to their particular needs.

The design also allows all of a patient’s health and medical informationto be available during a hospital stay or doctor’s visit. The latestinformation will then be immediately available to nursing homepersonnel, a homecare professional, an assisted-living aide or anyanother authorized HCP. The patient’s medical history will be available24 hours a day, 365 days per year anywhere in the world that hasInternet access.

Various business modules can be deployed in the integration platform. Inthe illustrative example, four business modules are included, includingfor example: office management (OMM) 32, human resources management(HRM) 33, minimal data set module (MDS) and customer billing (CBM) 34.

The office management module 32 provides employee and customerscheduling services. Patients can make appointments online and thesystem will confirm by phone, e-mail or text message the patient’sintent to visit the doctor at the designated time. The system will alsoprovide resource management for exam rooms, test devices, and otheroffice resources. The system will calculate and display performanceinformation such as the number of patients treated in a specific timeperiod, the amount of time spent with each patient, the number ofprescriptions written in a specific time period, etc. The system canmanage multiple locations for the same organization and compare theperformance of multiple locations.

The human resource module 33 manages all data and information related toemployees. A healthcare provider (HCP) can manage their personal andcertification information with the HRM. The HCP can upload copies ofrequired certification information such as a copy of a driver’s license,fingerprints, ongoing education course completion certificates, criminalbackground checks, etc. The user may set a date to be notified by phone,e-mail or text message of the impending expiration of criticalinformation. The system will come with a set template for certificationinformation but the user may add additional items to the list to createa customized version of their professional experience.

The HRM 33 will also allow HCPs to automatically transfer HR databetween organizations. All files and other information will betransferred from the HCPs personal file to the potential employer’sonline application system. A notice will be sent to both parties if anyinformation is missing or if the application is incomplete.

The HRM 33 will also monitor the hiring process. Once an employmentapplication is complete, the responsible party will be notified that theapplication is ready for review. When the application is reviewed, thereviewer can accept the application and schedule an interview. Theinterviewer can notify applicant of the interview’s particulars, date,time, place, etc., with assistance of the system. If the applicant isrejected, the reviewer can notify the applicant using systemcommunications. If the applicant successfully passes the interview, theinterviewer may automatically transfer the applicant’s information intothe employee category.

The HRM 33 manages the employee’s experience and performanceinformation, as well as availability status, vacation time, performancehistory, etc.

The customer-billing module 34 tracks services provided to a patient byICD codes and automatically files the invoice to Medicare or pushes thebilling information into the organization’s financial system. Thetreatment tracking functionality will automatically prioritizetreatments per the number of occurrences in particular office.Consequently, each HCP office will have a customized tracking servicesheet instead of a standard list that may not be suitable for thatparticular office.

Finally, the MDS 35 module digitizes the standard MDS form, allows thehealthcare team to collectively review the patient’s treatment protocol,manages any changes to the patient’s treatment, tracks the patient’sprogress, and automatically calculates the patient’s score. Once theinformation has been approved by all of the healthcare team members, therequest for payment can be submitted directly toprovider/payer/Medicare.

The user portal 36 integrates and displays the information gatheredabout the patient in one place and in an intelligent fashion for easyreference. The portal information will provide an up-to-date snapshot ofthe patient’s condition and provide information to make better treatmentdecisions. The portal is customizable for each patient and user.

One advantage provided by the system is the integration of remotelygenerated information that is not currently available to a patient’shealthcare team. Some information is currently reported but many timesis simply written down and forgotten or not displayed in a useful mannerto the HCP so it is ignored. Remote data collection is especiallyhelpful in treating chronic diseases because the patient needs constantmonitoring. This amount of attention is difficult and expensive whendone by a caregiver but the situation is ideally suited for electronicmonitoring and feedback.

For example, as shown in the architecture of FIG. 2 , the system can beimplemented to perform medication adherence 37 and body weightmonitoring 38. In both cases, system hardware is employed to monitor apatient’s weight and the complete medication cycle.

In these example implementations, the system 37 tracks a prescriptionfrom the time it is prescribed, when the prescription is filled, whenthe patient picks up the prescription, when the medication is loaded inthe special dispenser. Once the medication is loaded into the dispenser42, the system automatically delivers the mediation into a container andnotifies the patient that it is time to take the medicine. Once thecontainer is removed and replaced, the system will automatically updatethe status of the medication from dispensed to taken.

An intelligent device 40 such as a smartphone or tablet operates adevice controller 41 to control the medication dispenser 42. Thedispenser 42 and remote service controller are connected by a wired-USBconnection. The controller is updated by the integration platform withthe latest medication regimen when any changes occur to the patient’smedication protocol. The dispenser 42 can hold more than a one-monthsupply of any pill-form medication. The user may dispense medication bymanually operating the dispenser so medication may be taken at adifferent location than where the dispenser is located.

A scale 38 connected to the remote service controller by a wired-USBconnection will measure body weight and input the results into thesystem. The patient’s weight history can be displayed in the user portalfor future reference.

Illustrative Embodiment

This section will now describe an illustrative embodiment of theinvention that implements a medication dispenser. The followingdescribes FIGS. 2-9 , which provide detailed schematics of thecomponents of a dispenser system according to some embodiments of theinvention.

In the example system, the medication dispenser will include “x” numberof base unit module(s) that hold one type of pill-form medication. Thebase unit module is designed to limit the amount of materials and costof the dispenser.

Communications between the dispenser 42 and information systemcontroller 41 can be handled over cabling, e.g., USB cabling.Alternatively, communications can be implemented using wirelesscommunications hardware.

Medication is handled only in single doses, e.g., one single pill, atall times in some embodiments. The standard medication dispenser 42 isconfigured with 12 base unit modules to manage 12 individual pill-formmedications. The same medication may be held in multiple base unitmodules 8. Each base unit module can hold up to 33 doses of anindividual medication.

Medication will be manually loaded into a base unit module 8, where thebase unit modules are easy to load. The base unit module design helpseliminate mistakes in loading medication. Preferably, only one base unitmodule can be open at a time in preparation for and during loading. Anoptional video system can record the loading of medication into the basemodule units.

If a base unit module 8 is opened at an unscheduled time, thedispenser’s monitoring system will be triggered and a history of theactivity will be recorded. Base unit modules will be sealed once theyare loaded. The dispenser’s software monitoring system will confirm thateach base module is sealed. The dispenser’s software monitoring systemwill confirm the number of pills in each base unit module.

The medication dispenser will dispense the types of medication in theamount(s) and at the time(s) prescribed in the patient’s medicationprotocol. Once the dispensed medication is confirmed to be the correctamount, the medication will be deposited in a receptacle and ready forconsumption. The dispenser’s monitoring system will confirm themedication is taken within a pre-determined time by noting the removaland replacement of the medication receptacle 19. If the medication isnot removed from the receptacle 19 within a predetermined time, a noticewill be sent to pre-determined, concerned parties.

In terms of information technology, the system notifies healthcare teammember(s) under various conditions. For example, a notification isprovided if a medication is not on the approved medication list and/orprovides notification that the dispenser may not operate properly. Thesystem can notify healthcare team member(s) that the system is notfunctioning properly.

The system 39 is configured to compare dispensedmedication-to-medication listed in treatment protocol. The system 39confirms that the correct amount of medication is dispensed. The system39 will notify healthcare team member(s) if an incorrect medication isdispensed. If the medication supply in a specific module is at or belowthe refill quantity, a notification will be sent to a concerned party.If a module 8 is empty, an urgent notification will be sent to severalconcerned parties. The system 39 will notify healthcare team member(s)if the incorrect type or incorrect amount of medication is dispensed.

After confirmation of the amount of medication the machine automaticallydeposits medication(s) into a cup. If the medication is not removed fromthe receptacle within a predetermined time, a notice will be sent topre-determined, concerned parties. The system 39 can also notify healthteam member(s) at predetermined levels of medication for refill.

If a patient is requested to perform other activities before takingmedication, the system 39 will prompt the patient to do theseactivities. Once the patient acknowledges these ancillary activities arecomplete, the system will dispense the patient’s medication.

In some embodiment, the medication routine is remotely updatable. Inaddition, the system can manage multiple users.

A motor driven cogged belt can be employed to implement the dispenserhardware. A separate belt compartment can be implemented for each pill.Each module 8 can be removed from the console unit with the motor driveleft in place in the console. The “Paddle Wheel” drive engages the cogsin the belt allowing easy removal of the module from the console 1. Themodule can be loaded either while in the console or removed for remoteloading and then replaced into the console. A separate DC drive motor 12drives each console with a worm drive 1 between the motor shaft and thedrive wheel, preventing “Back drive” while the module belt is parked.

The module 8 is designed such that pills can be loaded on both the frontand back sides of the belt. A sliding access door 27 is on the frontside of the module, but the belt can be rotated back to expose the emptycogged belt openings and load more pills, utilizing most of the beltlength. In some embodiments, the belt can hold about 36 separatemedications.

The use of a perforated belt 22 with pegs on the nose wheel providespositive ejection of the pill from contact with the belt.

The cross feed belt 15 delivers the medications from each of thedispensing belts to the collection cup. This feature allows the use of asmall collection cup 19 and a single pill delivery confirmation sensor18 is used on the cross feed belt, eliminating the need for a separateconfirmation sensor at each of the dispensing belts.

The pill collection cup 19 can be designed either from the front of themachine or from the side. The front location does require a longer drawto reach the cross feed belt exit point. Each feeder module has asliding lid covering the pill locations in the belt cogs. The overallconsole has a hinged lid that covers all the feeder modules and locksdown in place with an electro-mechanical locking system 6 that issoftware controlled and password protected.

The information/computer systems for this type of dispenser system havecertain control features. For example, feedback confirmation is providedfrom sensors 9 to record essential events. Inventory levels of thedispensed medications are identified for comparison to the restockingrequirements when the machine is to be refilled.

Translation is performed of the medication schedule into a “load map”showing where what medications are loaded into the machine.

In addition, information is provided to the machine control interface 39to actuate the proper motors and mechanisms. A medication collection cup19 presence and removal sensor is provided to interpret that themedication cup has been removed and replaced, inferring that the patienthas taken the medications.

The overall system will have a battery backup power system allowing thesystem to operate multiple days on battery power if necessary. Therecharging of the battery is accomplished through the console powersupply while the unit is under AC power.

Console

As shown in FIGS. 3-4 , the console is comprised of a plastic case 1which incorporates a support bracket 2 for the paddle wheel DC drivemotor 12 with worm drive 11 attached and a support 3 for pill modules 8.The case 1 provides attachment mechanisms 14 for a cross feed belt 4 andcross feed belt DC drive motor 16. A locking mechanism 5 secures themodules from tampering. An LCD display 7 display the system status. Theplastic module 8 seals the pill inventory from dirt. Mounting points 9contained in the case 1 allow sensors to be mounted in the case. Lockingmechanisms 10 allows manual locking and unlocking of the belt rotation,allowing for normal rotation of the belt. Sensors 13, 18 controlmovement of the belt and delivery of medication. The pill collection cup19 is controlled by a software-controlled locking mechanism 6, 20 thatsecures the pill collection cup 19.

Paddle Wheel Drive

The worm drive 11 is a tubular extension with screw threads on thepaddle wheel interface end and internal female threads on the DC motorface end and is connected to the DC drive motor 12. The DC drive motor12 drives the paddle wheel drive wheel. The DC motor 12 will not haveany integrated controls or sensors but will depend on feedback from thebelt position sensor system to signal when one place increment hasoccurred. A resident sensor 13 will determine the movement of exactlyone pill position. The DC drive motor 12 characteristics provide naturalresistance to back driving. Pill modules 8 can be easily engaged anddisengaged from the DC drive unit.

A sensor 9, 18 through beam transverses the entire width of the modules8, which allows the monitoring of belt/paddle wheel movement from anymodule with only one sensor. The sensor beam utilizes the spacingbetween the individual paddle wheel teeth as the clear path for thesensor beam. As the wheel rotates, the rotating wheel blocks the beamuntil the next space between the teeth aligns with the beam, signalingthat one belt increment has advanced on space.

Cross Feed Conveyor

The cross feed conveyor 15 is supported by and contained in thedispenser housing and is driven by a DC motor coupled to a pulley on oneend. The conveyor belt will have raised bumps to prevent the pill fromrolling against the conveyor sidewalls. The side rails 17 are flaredoutward, providing a wider path to catch the pill as it is released fromthe module belt and falls onto the cross feed conveyor belt. The DCdrive motor 12 will not have any integrated controls or sensors butdepend on feedback from the pill arrival sensor system to signal wheneach pill has arrived at the collection cup and the cross feed belt canstop. A sensor 18 identifies that each pill has reached the collectioncup. Only when each individual pill has arrived at the collection cup 19will the operation sequence for the next pill begin. This sequenceensures that the complete and proper operations for each pill areperformed and verified before operations for the next pill begin.

Pill Collection Cup

The pill collection cup 19 has a custom shape to prevent the user fromsubstituting other generic containers. A software-controlled latch 20will prevent cup removal before the pill dispensing sequence is completeand when the dispenser is idle.

Pill Dispensing Module

The pill-dispensing module 8 is constructed of all molded plastic parts.The module belt design 21 provides for containment and separate of eachindividual pill. Each pill compartment is defined by the belt cleats,front and back, and by the module side rails on each side of the pillcompartment. The pill-dispensing module is loadable while separated fromthe console. A belt rotation-locking feature prevents the belt fromrotating when the module is separated from the console. This lockingfeature can be manually disengaged to rotate the belt during the loadingsequence. The pill capacity of each module is achieved by loading boththe front and back sides of the module belt. Loading involves initiallyloading a portion of the pill capacity on the front side and thenrotating the belt to load the remaining portion on the backside of thebelt.

Quick engagement with the paddle wheel drive is a key feature of theoverall system 24. The feature allows the quick removal and replacementof the modules from the console. The ease of removal and replacement isachieved through the self-aligning engagement between the paddle wheeldrive and the cleat features in the belt. As the module is inserted inthe console, the belt rotation lock 23 is released first, which allowsthe belt to self-align with the drive paddle wheel. With the drivepaddle wheel position maintained by the through beam sensor, the beltwill self-align to the proper “parked” position. The perforated beltwith ejector pins 25 is used to ensure that the pills do not stick tothe base of the belt. The drive pins also service as ejector pins tolift the pills off the base of the belt as the pill arrives at the dropposition at the bottom dead center.

A raised bump 26 on the module housing ensures that the pills do notremain stuck on the belt. As each cleat encounters the bump on themodule housing, each divider is flexed, which creates a flicking actionto break loose the sticking pills from the divider cleat.

Each module has its own lid 27 to prevent losing pills during loadingand transport. The individual module lids are a sliding strip thatuncovers the belt for loading and is returned to closed for transportingand reinstallation to the console. A locking feature prevents the beltfrom turning after the module is loaded and before it is returned to theconsole. As discussed in the module loading section, each module belt islocked from rotating when removed from the console to preventinadvertent spillage of the pills during handling of the module. Thelocking feature can be manually disengaged to rotate the bell to anotherposition while loading pills. Once manually released, the belt relocksuntil the module is returned to the console. A feature in the consolereleases the lock while the module is in the console, allowing normalrotation of the belt.

The materials used to manufacture the dispenser parts include at leastsome or all of the following: 1) Belt- molded urethane, 2) Housing -Injection molded plastic, 3) Belt pulleys - Injection molded plastic, 4)Sliding Lid - Extruded plastic and 5) Locking mechanism - Injectionmolded plastic.

Additional Features of the Illustrative System

The system is designed to be easy-to-use and maintenance and worry free.To achieve these goals, the device does not require any installation,maintenance or IT skills to setup or use. Device functionality isaccessible on any Internet enabled device, such as, a PC, tablet orsmartphone. Information generated by the patient is stored in acloud-based system so backup of vital information is completedautomatically and with a high level of security is assured. The systemrequires a password, passcode, fingerprint, facial scan or other secureinformation input to gain system access. The system is designed to alloweasy integration with other systems to expand functionality and providea seamless interconnection between all caregivers including physicians,pharmacist and patient. The system allows an administrator to manageseveral machines at multiple locations

The system automatically checks for drug interactions when aprescription is initially written and when there is a change to apatient’s medication regimen. If a negative drug interaction isidentified, the concerned members of the healthcare team are notifiedimmediately. System security ensures that only authorized healthcareproviders make adjustments to a patient’s medication regimen. The systemautomatically notifies the patient when to request a refill and alsoenables the patient to make medication refill requests electronically.The patient may change the location of the refill if so desired and thepatient is notified of how many refills are remaining on theprescription. The system notes when a prescription is filled and can beconfigured to track the return of unused medications to a pharmacy orother disposal location.

The system will notify the healthcare provider which medication needs tobe changed and indicate which module contains that particularmedication. The system also tracks the number of doses loaded, thenumber doses remaining and prompts the patient or healthcare provider toconfirm that the medication was taken. The system also records and savesa patient’s medication history.

The Medication Dispenser Component

The device holds and manages up to 12 different types of pill-form orcapsule medications and can hold up to 40 doses of each medication. Amonth’s supply of all 12 medications, 480 doses, can be loaded inapproximately 20 minutes by a capable individual. After the medicationsare loaded, the device does not require patient or healthcare providerinteraction to operate. The device does require user authorization toaccess or open the dispenser for loading or other adjustments. Access iscontrolled by a password, passcode, fingerprint and/or facialrecognition and all access events are recorded and saved in a devicehistory log that is available to each member of the healthcare team. Thedevice will notify the patient and other healthcare team members that amedication needs to be changed and the device will not operate until themedication change is confirmed by an authorized use and is logged by thedevice. The device will signal that the device is unlocked and a moduleis open for loading. If more than one module is open, the dispenser willprompt the user to close one of the open modules. When medication isdispensed the device confirms that the medication has been depositedonto the transfer belt and also that the medication has been depositedinto the dispenser cup. Optional features include a bar code reader forcoded medications and a hardened case for increased security.

Additional Embodiments

FIGS. 10A-C illustrate an embodiment of a belt and cog assembly that isplaced inside a module/cartridge. The belt 57 is formed by assembling aset of cleats 43 that are movably affixed together using a set of pins45. FIGS. 11A-E illustrate an example cleat and FIGS. 12A-D illustratean example pin. Each pair of cleats are attached by inserting pin 45into opening 65. A closed sequence of such pairs of cleats 43 affixedusing pins 45 is assembled to form belt 57. The belt 57 is driven bycogs 44 to rotate in a defined direction. This allows medication placedwithin medication pocket 56 to shift in a controlled manner around themovement path of the belt 57.

As illustrated in FIGS. 13A-B, a module/cartridge 52 (hereinafterreferred to as either “module” or “cartridge”) is assembled by placingthe belt and cog assembly inside a cartridge body. FIG. 14 shows astacked set 49 of cartridges 52. In the embodiment of FIG. 15 , thecartridges 51 are horizontally aligned relative to a transverse belt 15,rather than having a vertical alignment as shown in FIGS. 3-4 .

FIG. 15 illustrates a set 51 six medication cartridges 1-6 that employthe cartridges 52 of FIGS. 13A-B. The cartridge body includes twoindependent sides connected by hinges 48 on the top of the cartridgethat are joined and securely closed by a screw 46 on corners of thecartridge. In some embodiments, the medication cartridge is formed usingfood-grade vinyl or similar food-grade material that has desiredperformance characteristics of an intended application. The cartridgemay also include an opaque cover for the drive mechanism, a clearretainer/cover for the medication belt, and/or retaining magnets 54 forthe medication retainer/cover.

In terms of manufacturing and assembly, some or all of the components ofthe medication cartridge can be manufactured by 3D printing or injectionmolding. With respect to the electric drive motors 55 in FIG. 15 , gearsand wiring are added to each central cavity side of a cartridge half inFIGS. 13A-B. Hinges 48 that are attached to the top of the cartridge 52join the two sides of a cartridge half. The sides of the cartridge 52are then securely closed by the addition of a screw 46 at each corner ofthe cartridge body.

Next, two cogs 44 and a belt 57 are added to the outer section of eachside of each cartridge. The belt is preassembled by inserting a connectpin 45 (as illustrated in FIGS. 12A-D) between two cleats 43 (asillustrated in FIGS. 11A-E) in the connection holes 65. A clear closurecover is attached to each side of the cartridge along with closuremagnets 54 at the bottom corners of the cartridge.

The assembly includes a sweeper cleat 50 as shown in FIG. 15 . Thesweeper cleat 50 is used to ensure that any mediation that adheres tothe belt pocket will be removed and deposited onto the transverse beltand ultimately to the dispenser cup.

When the screws 46 in FIG. 15 are removed, the user has access to thecenter cavity of the cartridge 52, which is formed when the two sides ofthe cartridge are joined together by the screws. The center cavitycontains the electric drive motors 55, cogs 44, and gears of the drivemechanism.

The motor 55 in FIG. 15 can be chosen for its physical size, torque andmovement characteristics, to provide precise control of the belt’smovement. The cog 44 is connected to an electric drive motor 55 by adrive gear. In some embodiments, the ratio between the cog 44 and theelectric motor drive gear is selected to provide an amount of movementto advance the medication belt precisely one position.

The medication belt is driven by the movement of the cogs 44, which isdriven by the electric drive motors 55. The medication belt is composedof cleats 43 in FIGS. 11A-E and assembly pins 45 in FIGS. 12A-C. In someembodiments, a belt includes 34 cleats 43 and 34 pins 45. A customlength belt can be created by increasing or decreasing the total numberof cleats in the belt. When two cleats are connected together with theconnection pins, they form a medication pocket 56 in FIG. 10B that insome embodiments measures 1″ tall by 0.4″ deep by 0.5″ wide.

With the finished assembly, the process to deliver medication to thedispenser cup 19 is initiated in one of two ways: 1) the user issues acommand from the dispenser controller to dispense the medication or 2)the dispenser notifies the user audibly and/or visually that it is timeto take their medication and the user presses a control mechanism on themachine to initiate the medication delivery.

Once the dispenser receives the input from the user to deliver themedication, the motor 55 for each designated cartridge 52 will turn theprecise distance to advance the medication belt 57 exactly one space.Once the selected belts advance one space, the transverse sweeper belt15 will move the entire width of the dispenser to ensure delivery of allmedications to the dispenser cup 19. In the embodiment of FIG. 15 , itis noted that the cartridges 52 are horizontally aligned relative to thebelt 15.

There are numerous advantages to this embodiment of the dispensingassembly. With regards to the belt, no glues or other hazardousmaterials are used in the assembly process. In addition, significantlylower costs can be achieved, at least as compared to belt cost usingalternative injection molding solutions. Moreover, improved performancecharacteristics can be achieved when compared to injection moldingalternatives. Twisting or bending technical issues are resolved by thecleat/pin design and using relatively stiff construction material.Stiffer materials also allow more precise manufacturing which permitsthe medication to be handled more precisely to reduce medicationbreakage or binding in the mechanism. The angles of the medicationpocket can be configured as illustrated in the figures to allow themedication to be scooped off the cartridge floor and not pinch under thefollowing cleat, and the angles hold the medication when it is beinglifted or lowered during transport. In addition, the belt length can beadjusted to accommodate more or less medication.

Therefore, what has been described is a cloud-based resource andinformation tracking system for medical patients and healthcareproviders. The cloud-based software system integrates all or manysources of patient medical and health information, updates theinformation in near real-time, and makes the data available to member(s)of the patient’s healthcare team securely.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. It will, however, be evidentthat various modifications and changes may be made thereto withoutdeparting from the broader spirit and scope of the invention. Forexample, the above-described process flows are described with referenceto a particular ordering of process actions. However, the ordering ofmany of the described process actions may be changed without affectingthe scope or operation of the invention. The specification and drawingsare, accordingly, to be regarded in an illustrative rather thanrestrictive sense.

1. An automated pill dispenser, comprising: a plurality of pilldispensing modules, the plurality of pill dispensing modules having afirst pill dispensing module and a second first pill dispensing module,the first pill dispensing module having a first dispensing belt thatdispenses a first individual pill and the second pill dispensing modulehaving a second dispensing belt dispenses a second individual pill; eachof the first and second dispensing belts driven by a drive motor,wherein each of the plurality of dispensing belts corresponds to aseparate medication for delivery; and a sensor that monitors operationof the automated pill dispenser for dispensing medication by theplurality of pill dispensing modules.
 2. The automated pill dispenser ofclaim 1, further comprising a cross feed belt that delivers themedication from the plurality of dispensing belts to a collection cup,wherein the sensor corresponds a pill delivery confirmation sensor. 3.The automated pill dispenser of claim 2, wherein the pill deliveryconfirmation sensor corresponds to a single pill delivery confirmationsensor that is used on the cross feed belt without using a separateconfirmation sensor at each of the dispensing belts.
 4. The automatedpill dispenser of claim 2, wherein the sensor controls movement of thecross feed belt and delivery of the medication.
 5. The automated pilldispenser of claim 2, wherein the sensor corresponds to a pill arrivalsensor that signals when a pill has arrived at the collection cup. 6.The automated pill dispenser of claim 5, wherein the pill arrival sensorsignaling that the pill has arrived at the collection cup causes thecross feed belt to stop.
 7. The automated pill dispenser of claim 2,wherein the pill delivery confirmation sensor provides deliveryconfirmation data for recordation.
 8. The automated pill dispenser ofclaim 7, wherein inventory data is analyzed in conjunction with thedelivery confirmation data to identify refilling requirements for theautomated pill dispenser.
 9. The automated pill dispenser of claim 1,wherein the sensor provides feedback confirmation to record events forthe automated pill dispenser.
 10. The automated pill dispenser of claim1, wherein the sensor monitors for removal or replacement of amedication cup.
 11. The automated pill dispenser of claim 1, wherein thedrive motor has a ratio relative to a cog of the dispensing belt suchthat the first dispensing belt or the second dispensing belt has amovement amount of one mediation dispensing position.
 12. The automatedpill dispenser of claim 11, wherein the sensor corresponds to a beltposition sensor system that signals when one mediation dispensingposition increment has occurred.
 13. The automated pill dispenser ofclaim 12, wherein the drive motor does not have an integrated sensor,but where feedback from the belt position sensor system is used forsignaling when a one place increment has occurred.
 14. The automatedpill dispenser of claim 1, wherein the sensor corresponds to acollection cup sensor that identifies removal and replacement of acollection cup.
 15. The automated pill dispenser of claim 1, furthercomprising a lock affixed to a case that contains the automated pilldispenser.
 16. The automated pill dispenser of claim 1, furthercomprising a belt rotation lock that prevents the first dispensing beltor the second dispensing belt from rotating when a respective pillmodule is disengaged from the automated pill dispenser.